The consensus as I read it was accessibility should be such that no one is disadvantaged by disabilities unnecessarily and that means that they should make online discounts accessible to all by making their website accessible [according to WCAG standards].
In the UK this is required by the Disability Discrimination Act, companies have to make "reasonable" adjustments to enable access (where reasonable is inter alia a function of the costs and business size too).
I understand that USA have a DDA too with a very similar requirement and so it appears that no new legislation is required to get Domino's to act, just a court order or someone at Domino's deciding they care about accessibility.
If your startup has assessed the question of accessibility, documented it, not actively worked against accessibility, done whatever internal leads consider reasonable within its cost constraints (eg, where costs allow asking/employing experts), then you're on track.
Same goes for having a store with a step at the front.
If you're making millions in revenue [through your website] but won't create an accessible colour scheme, or provide Aria tags, skip links, image descriptions, and such that are pretty much standard boilerplate nowadays then you deserve to be hauled up on it, IMO.
Accessibility is important, but things like this can easily overstep their bounds to the degree that it can stifle competition. It would've made far more sense to work towards some unified OS features that would allow for such functionality, instead of putting the burden onto the application developer.
[0] https://www.3playmedia.com/2019/03/18/the-cvaa-video-game-ac...
Except Electron, where you get to reimplement everything.