<html><head><meta http-equiv="Content-Type" content="text/html charset=us-ascii"></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space;"><br><div><div>On Apr 24, 2014, at 11:06 AM, Douglas Fish <<a href="mailto:drfish@us.ibm.com">drfish@us.ibm.com</a>> wrote:</div><br class="Apple-interchange-newline"><blockquote type="cite"><br>I've proposed a design session for accessibility for the Juno summit, and<br>I'd like to get a discussion started on the work that needs to be done.<br>(Thanks Julie P for pushing that!)<br><br>I've started to add information to the wiki that Joonwon Lee created:<br><a href="https://wiki.openstack.org/wiki/Horizon/WebAccessibility">https://wiki.openstack.org/wiki/Horizon/WebAccessibility</a><br>I think that's going to be a good place to gather material. I'd like to<br>see additional information added about what tools we can use to verify<br>accessibility. I'd like to try to summarize the WCAG guidelines into some<br>broad areas where Horzion needs work. I expect to add a checklist of<br>accessibility-related items to consider while reviewing code.<br><br>Joonwon (or anyone else with an interest in accessibility): It would be<br>great if you could re-inspect the icehouse level code and create bugs for<br>any issues that remain. I'll do the same for issues that I am aware of.<br>In each bug we should include a link to the WCAG guideline that has been<br>violated. Also, we should describe the testing technique: How was this<br>bug discovered? How could a developer (or reviewer) determine the issue<br>has actually been fixed? We should probably put that in each bug at first,<br>but as we go they should be gathered up into the wiki page.<br><br>There are some broad areas of need that might justify blueprints (I'm<br>thinking of WAI-ARIA tagging, and making sure external UI widgets that we<br>pull in are accessible).<br><br>Any suggestions on how to best share info, or organize bugs and blueprints<br>are welcome!<br></blockquote><div><br></div><div>Doug,</div><div><br></div><div>Thanks very much for bringing this up as a topic and pushing it forward at Summit. I think this will be a great step forward for Horizon in maturity as we continue to have better accessibility support. I wanted to throw out any article that I found helpful when it comes to testing sites for accessibility for colorblindness:</div><div><a href="http://css-tricks.com/accessibility-basics-testing-your-page-for-color-blindness/">http://css-tricks.com/accessibility-basics-testing-your-page-for-color-blindness/</a></div><div><br></div><div>I think we can make some very small/easy changes with the color scheme to be sure there is enough contrast to target all types of colorblindness.</div><div><br></div><div>Looking forward to this session,</div><div>Liz</div><br><blockquote type="cite"><br>Doug Fish<br>IBM STG Cloud Solution Development<br>T/L 553-6879, External Phone 507-253-6879<br><br><br>_______________________________________________<br>OpenStack-dev mailing list<br><a href="mailto:OpenStack-dev@lists.openstack.org">OpenStack-dev@lists.openstack.org</a><br>http://lists.openstack.org/cgi-bin/mailman/listinfo/openstack-dev<br></blockquote></div><br></body></html>