[Tex2002ans]

Originally Posted by Hitch

Spoiler:

What accessibility standards are you able to adhere to in your ePUB conversion?
We are looking for a minimum of WCAG 2.0.
Are you able to meet these and if so, how does it affect your pricing?

Well, I would probably just promote the parts of your workflow that do make books "as accessible as possible":

• Use very clean markup
• Take pride in marking things properly
  
  • Headings as <h1>, not <p class="heading">
    
  • <i>, not <span class="italics">
• Night Mode support
  
  • No black-on-black text
• Tables as <table>, not pictures of data
• Foreign letters as actual text, not as little images.
• Use proper lang + xml:lang
• Proper alt text
• [...]

Originally Posted by Hitch

I mean...if you're gonna be an accessibility badass, don'tcha think you should at least READ the damned standards? And pay attention to the fact that they're for THE WEB, not eBooks, where things like "make it easier for users to hear or see the content" are ENTIRELY in the control of the device-and-firmware makers, ffs?

Perhaps they heard the "Accessibility" buzzword, and know it's a good idea to create more accessible documents, but don't know some of the technical details behind it.

A few examples of talks:

• ebookcraft 2017 "Creating a Roadmap for Accessibility"
  
  • Talk given by MIT Press.
    
  • (I would recommend just starting the video at 18 mins+.)
    
  • They discuss WCAG 2.0 a tiny bit, but point towards EPUB Accessibility 1.0, which gives some extra ebook-specific stuff to aim for (and says to "must meet WCAG 2.0 Level A", but aim towards Level AA.)
• ebookcraft 2017 "Ebook Usability from Library's Perspective"
  
  • Accessibility discussed around 24 mins + 41 mins.
    
  • They also mention potential "legal requirements" which might aim for a WCAG level.
    
• ebookcraft 2019 "The Accessibility Supply Chain"
  
  • Explains some of the issues you might run across in books, plus discussing more of a business use-case on why things need to be designed Accessible in the first place.

So meh. I probably would've just given the bulleted list, then pointed to a few other resources and say you do your best to follow WCAG as much as possible without sacrificing compatibility with actual stores/devices.