E-mail List Archives
Thread: Test pages with WCAG-errors
Number of posts in this thread: 4 (In chronological order)
From: Morten Tollefsen
Date: Wed, Aug 23 2017 3:47AM
Subject: Test pages with WCAG-errors
No previous message | Next message →
Dear all.
(sorry if this has already been posted on the list, but I've not been able to find it)
I know this topic has been discussed before and thought this could be worth mentioning.
Trond Ausland and I have started to create a set of web-pages with WCAG errors. As a starting point we use SortSite rules, but we have also included some other errors (and rules which is not tested good enough by SortSite). An evaluation link to wave is also included on each test page.
The work is not completed! However we're of course thankful for feedback! More errors will be added in the weeks to come.
Why creating this pages: well, to gfigure out what evaluation tools are able to check. And perhaps even more important (for us) to use the pages combined with different exercises in our training courses and evaluation work.
Even if these pages are part of a Norwegian wordpress blogg about accfessibility and web/apps the test pages are not included in the wordpress framework. The language is English (the blogg is in Norwegian).
URL: http://eksempelsamling.medialt.no/wcag-errors/
BR: Morten Tollefsen
From: Jennifer Sutton
Date: Wed, Aug 23 2017 11:32AM
Subject: Re: Test pages with WCAG-errors
← Previous message | Next message →
Hello:
I think this kind of thing has been done before, and perhaps several
times. Maybe there could be some collaboration to maximize resources . . .
See this, as one example that came immediately to my mind. Perhaps
others know more:
http://aduggin.github.io/accessibility-fails/
Jennifer
On 8/23/2017 2:47 AM, Morten Tollefsen wrote:
> Dear all.
> (sorry if this has already been posted on the list, but I've not been able to find it)
>
> I know this topic has been discussed before and thought this could be worth mentioning.
>
> Trond Ausland and I have started to create a set of web-pages with WCAG errors. As a starting point we use SortSite rules, but we have also included some other errors (and rules which is not tested good enough by SortSite). An evaluation link to wave is also included on each test page.
>
> The work is not completed! However we're of course thankful for feedback! More errors will be added in the weeks to come.
>
> Why creating this pages: well, to gfigure out what evaluation tools are able to check. And perhaps even more important (for us) to use the pages combined with different exercises in our training courses and evaluation work.
>
> Even if these pages are part of a Norwegian wordpress blogg about accfessibility and web/apps the test pages are not included in the wordpress framework. The language is English (the blogg is in Norwegian).
>
> URL: http://eksempelsamling.medialt.no/wcag-errors/
>
> BR: Morten Tollefsen
>
> > > >
From: Jennifer Sutton
Date: Wed, Aug 23 2017 12:35PM
Subject: Re: Test pages with WCAG-errors
← Previous message | Next message →
Greetings, again:
Actually, this is the link to the outcome, and it's what I was
originally looking for:
https://alphagov.github.io/accessibility-tool-audit/
And while looking for it, I found other items that some may find of
interest, so I will include below my name. As with all things in
accessibility-land, mind the dates!
While some of what's below results in "tool outcome comparisons," my
point in including is to offer suggestions of places that show tests.
I also think, at one time (anyway), there was a W3C automated testing
community group that was working on this kind of thing, so perhaps that
work would be worth tracking down. And here is a place to start:
https://www.w3.org/community/auto-wcag/
Best,
Jennifer
[who works hard, as a volunteer, every day, to try to prevent duplicated
effort. People complain that accessibility is hard and expensive, and it
seems to me that a big reason why is "wheel re-invention. I get that
some of this becomes about "intellectual property," but maybe sharing
tests, and monitizing the UI/making it efficient for *all* users could
be a resource generator.]
These two go together:
http://iktforalle.no/accessibility-checker-evaluation/overview.html
and
http://iktforalle.no/accessibility-checker-evaluation/objective_evaluation.html
This CSUN 2016 presentation by Terrill where he tests against Accessible
University (with its known 18 issues):
http://terrillthompson.com/blog/730
And then, of course, there's the WAI's own Before and After Demo which
certainly offers some tests:
http://www.w3.org/WAI/demos/bad/
From: Morten Tollefsen
Date: Fri, Aug 25 2017 5:08AM
Subject: Re: Test pages with WCAG-errors
← Previous message | No next message
Hi!
Yes, as I also mentioned this topic has been discussed before.
I need stabile pages which I have full access to, and therefore I've designed my own. If others can use the pages, perhaps learn something, it is great. If not, just forget the message:-). When this is said, collaboration is of course a good idea! These pages are not very complex, but everything can be used, copied, ... by everybody, no copyright or other restrictions.
I have not tried to include as many errors as possible on one page. This is a bit different from many other error examples I've seen. The reason is that I need to be able to scan multiple pages to be able to test some success criterias, but also to be able to exemplify spesific errors when training developers. So far it is 11 pages, and I suppose we'll need a couple more. I'm also going to do some fine tuning, but the result will look much like the pages as they are now. I'll also include 2.1 tests, probably on one page to be able to change when/if changes in the standard occure. Most errors, can be found with validators, but not all, and I'll include more errors wich need human testing as well.
Some pages, e. g. p011 show how different validators are on some success criterias. wave reports 0 errors (2 warnings). In comparison SortSite reports 6 errors. One error is an onchange handler in a select. Exactly the same functionality could havve been achieved with other coding (window.open, a function etc), and then SortSite would not have reported an error. And this is also one of my own motivations, to be able to know validators in detail (when do they report errors, what is not triggered etc). Many SortSite rules require very spesific code, and some of the rules are really not very robust!
http://x.medialt.no/wcag-errors/
BR: Morten Tollefsen
90899305, www.medialt.no