I do use the online menu sometimes, or use my phone camera to zoom in on the menu. Another way is to usually order from places which I frequent and do know the menu.

I use the online menu. If they don't have an online menu, I don't go there.

I checked out your menu and I must say it's a very impressive variety of accessibility tools you've got their, though of course I can't test allot of them my self as I'm totally blind.
I'm particularly interested by the built in screen reader option (chromevox?) as I didn't realize how full fledged it was.


Here are my thoughts.
1. I would put the language chooser at the top under accessibility, as it's very important and should be seen right away.
2. I noticed that you don't use level3 headings. I find that a bit strange especially when I saw that in the dessert section for instance, you grouped multiple items under the same sub category with no heading for each item, which would have been better.
3. I see that their is an unlabeled button above each item which reads as only a number and when pressed the state changes with no proper context.
4. There is an image link with no alt text above each item. If these can be hidden from a screen reader while still displaying the item pictures on screen, that would be great.
5. There is an unlabeled clickable element at the end of each section that doesn't seem to do much.
6. When I hit enter on the clickable labeled with the price, I'm taken to a quantity chooser. This should have a contextual label for the edit field and I would also make it so that hitting enter on the item heading only does this instead of the price as that is much less confusing. Also, you should know that most screen readers do not read - by default so you may wish to spell out minus for the - button, or rename them to add and subtract.
7. At the end of the page, their are a few fields that really need to be labeled, and especially those radio buttons.
8. I think that some of the accessibility options such as "cursor" and "tooltips" " could be given more explanatory labels, and that maybe "screen reader" should be changed to "have the menu read out loud" or something like that so that screen reader users know it isn't for changing to a screen reader accessible version of the menu, and so that low vision users who may want the menu read will know more what it means, as the word "screen reader" is still not in the public vocabulary.
9. I notice that most items don't have expanded descriptions of the dish, I assume this isn't an oversight but simply a lack of data for testing?

I always ask at chain restaurants if they have a braille menu, which they rarely do but unlike smaller ones who couldn't really afford it, it's at least a possibility...
Then, if they do, I make sure to check the date of production on the menu as they are often out of date.

Otherwise I try to find it online before hand so that I don't have to scramble at the table, and if I can't find it my self I'll call and ask if they have a web address for one.

Failing that I use a good document reader app like Voice Dream Scanner and it usually works quite well as most restaurants have good lighting and large text on their menus.

And if none of that is working or isn't fast enough, I'll just ask for a quick rundown of categories from the server and ask for more info about the categories I most care about/what they suggest in them.

I tend to use Google Maps or the place's website. Granted small places are less likely to have a menu up, but a growing number do.
Worst case, of course I take pictures and OCR but I've not had to do that this year at least.

I'm asking because I'm working on a digital menu and would like it to be the go-to solution vision impaired people would ask for.