Hmmmm, maybe I should have Haphaestus read out each link you navigate to by default? I was already planning to have a feature to read the whole page aloud, in part just to give the VCR buttons something to do & because I've already implemented that!
I'd still probably recommend my Rhapsode web browser over Haphaestus to the blind. But still, no need to exclude them from using my "smart" TV browser!
It's interesting how many CSS properties I'm finding might be relevant for Haphaestus to support! Many of the normal visual CSS properties ofcourse, but also print styles to paginate webpages in place of scrolling, & might as well throw in voice support to!
I thought I was trying to simplify the web!
To be clear blind people are not the only disability that we need to make our software accessible to. But they are perhaps the most alien to all the designers & developers thinking in terms of how their apps communicate visually.
Greater accessability is a major goal in my browser engine development, and I will enforce webdesign limits in it's name. And I'm trying to make it cool to even those who don't require it!
@alcinnz I agree here, a few thoughts.
1. Define what we think accessibility means then compare notes with others, and what any guide lines say about that,
2. We need to ensure the collaboration tools to gain feedback accessible so people can easily give feedback, even as non programmers (aka end users) , if there is a problem let them do their best to describe the issue either written verbally or with video, and the developers can take that and see what the issue seems to be.
3. accessibility is useful to everyone i have seen many websites that have say light text on a white background or a black background and grey ish text, why, it makes said text harder to read
4. Surely software / services should have security, privacy and accessibility considered from the ground up, right from the wire framing stage with lots of feedback from users as you develop that application or service.
I agree we need to make accessibility normal not just cool, it needs to be part of the design ethos . A good way to reach out to people who are not interested in programming but empower users to give feedback and act on the consensus this brings in
