| Info | ||
|---|---|---|
| ||
This is a draft of a plan to target WCAG 2.0 Level AA in uPortal that we hope to complete, discuss, and ratify in the community. Following that, we plan to convert this document to Markdown and commit it to the main uPortal repo in Github. |
...
| Issue | Technique | Notes |
|---|---|---|
| This fieldset element does not have a name available to an accessibility API. Valid names are: legend element. | Technique: H91 | See technique for ways to solve issue. |
| Duplicate id attribute | Technique: F77 | See technique for ways to solve issue. |
| This text input element does not have a name available to an accessibility API. Valid names are: label element, title attribute. | Technique: H91 | See technique for ways to solve issue. |
| This checkbox input element does not have a name available to an accessibility API. Valid names are: label element, title attribute. | Technique: H91 | See technique for ways to solve issue. |
WCAG
508
...
| . |
...
General Guidelines (for level A and AA)
...
- Webaim's Color Contrast Checker is a great way to check if you're color scheme adheres to Level AA.
- Webaim Web Accessibility Evaluation Tool scans an entire page and shows all accessibility issue. One caveat is this tool will only work for public websites. Sites with login access cannot be scanned.
- total11y is a Chrome extension that handles what Webaim Web Accessibility Evaluation Tool does, but as an extension to your browser.
- Accessibility Developer Tools is an accessibility audit tool built by Google Accessibility as a Chrome extension. (Github source)
- HTML_CodeSniffer is a client-side script that checks HTML source code and detects violations of a defined coding standard. HTML_CodeSniffer is written entirely in JavaScript, does not require any server-side processing and can be extended by developers to enforce custom coding standards by creating your own "sniffs". This was the tool used for the Oct 2016 uPortal accessibility audit. (Github source)
- Pally - your automated accessibility testing pal. It runs HTML CodeSniffer for programmatic accessibility reporting.
- Dashboard: Web interface for automated accessibility reporting and graphing. (Github source)
- web service: A simple JSON web service for automated accessibility reporting. (Github source)
- command line: Run one-off accessibility reports from the comfort of your command line. (Github source)
- Tanaguru is a free/open source software (AGPL licensed) for web sites assessments. (Github source, Discussion Forum, Jenkins plugin)
- Audits include a page audit, entire website audit (Heritrix crawler embedded), offline file audit and scenario audit which is a user path over a given website.
Crawling with credentials
It looks like this would be technically feasible. See https
WCAG
- Understanding WCAG 2.0 (http:// webarchive
- www. jira
- w3. com
- org/ wiki
- TR/ display/Heritrix/HTML+Form+GET+or+POST
- Here is the place in the tanaguru code where you would add the credentials. https://github.com/Tanaguru/Tanaguru/blob/master/engine/crawler/src/test/resources/full-site-crawl-conf/tanaguru-crawler-beans-site.xml#L439, or maybe if that doesn't work try here: https://github.com/Tanaguru/Tanaguru/blob/master/engine/tanaguru-resources/src/main/resources/conf/context/crawler/tanaguru-crawler-beans-page.xml#L452.
- UNDERSTANDING-WCAG20/)
- How to meet WCAG 2.0 (http://www.w3.org/WAI/WCAG20/quickref/)
- Web Accessibility Initiative (WAI) (http://www.w3.org/WAI/)
- WebAIM’s Introduction to Web Accessibility (http://webaim.org/intro/)
- WebAIM’s Resources page (http://webaim.org/resources/)
- WebAIM’s WCAG 2.0 checklist (http://webaim.org/standards/wcag/checklist
So something like this (with a valid login/password):
<bean id="credential" class="org.archive.modules.credential.HtmlFormCredential"> <property name="domain" value="example.com" /> <property name="login-uri" value="https://example.com/login"/> <property name="form-items"> <map> <entry key="login" value="mylogin"/> <entry key="password" value="mypassword"/> <entry key="submit" value="submit"/> </map> </property></bean>