I’m not sure why this thread returned. The dates of the last two posts are March 9, 2017.
Eh, I have experience with building accessible websites, so maybe some additional information will help.
Generally, you don’t design for all conceivable disabilities, you design to meet the guidelines related to accessibility. This is know as the Web Content Accessibility Guidelines (WCAG).
It’s a lot to know, so there’s software to make it easier to test a website…
Depending on the website, there might be stricter guidelines to follow. There’s a dramatic increase in difficulty when designing for WCAG A, AA and AAA.
Again, this can be done with a Timeline property. There are filters for “Contrast”, “Hue” and “Saturation”, which could be used to adjust the coloring of elements. By dropping the saturation to zero, and increasing the contrast, that could improve the view.
Here’s an example…
It’s an incomplete project. But in classic mode, the Hue and Saturation can be adjusted in the settings. (That game wasn’t designed to be accessible though.)
This is correct. Although, maybe a “Best Practices” document would be helpful. Normally, I don’t design Hype projects to be accessible. I just block the whole thing out with an ARIA tag.
Yet, it is interesting to think about what could be done with Hype to make life easier for people with disabilities. Large text, high contrast, voice over… this might be a good idea for a template. But if the settings are changed after the page is loaded, it probably wouldn’t pass an automated accessibility check.