E-mail List Archives
Thread: which are the things should keep in mind while doing content testing?
Number of posts in this thread: 12 (In chronological order)
From: Timy Sebastian
Date: Mon, Jun 26 2017 2:06PM
Subject: which are the things should keep in mind while doing content testing?
No previous message | Next message →
Hi all,
This is timy Sebastian from india, and this is my first mail to this group.
Please someone tell me, which are the things we should keep in mind
while performing the manuall content testing.
Kindly answer for some of my questions,
1. Do we have any guideline for the content testing?
2. Do we avoid links while performing a content test?
3. do we really care about the structure of the headings?
4. if the edit field doesn't have any appropriate label, and which is
inside the heading level one, will we reported?
kindly reply
With regards,
Timy.
From: Sean Murphy
Date: Tue, Jun 27 2017 2:41AM
Subject: Re: which are the things should keep in mind while doingcontent testing?
← Previous message | Next message →
It sounds like you are not concern with the structure of the document. AS Labels, headings and links are related to the structure. So what are you trying to validate?
AS the structure is just as important as the content.
Sean
From: Sarah Jevnikar
Date: Thu, Jun 29 2017 7:44AM
Subject: Re: which are the things should keep in mind while doingcontent testing?
← Previous message | Next message →
Hi Timy,
A great place to start is the WebAIM checklist, found at
http://webaim.org/standards/wcag/checklist
A list of testing tools can be found here:
http://webaim.org/articles/tools/
Also, if you're new to the accessibility field, Deque University offers free courses for persons with disabilities (I assume you are a screen reader user). Find the listing of courses here
https://dequeuniversity.com/
To answer your questions:
"1. Do we have any guideline for the content testing?"
See the WebAIM checklist link above. The guidelines for testing in general is WCAG 2.0. Whether it's Level A, AA, or AAA will depend on the guidelines given to you by your employer or government (if WCAG 2.0 is enforceable by law in India, I apologize for my ignorance; I don't know this)
2. Do we avoid links while performing a content test?
I wouldn't avoid links - you need to ensure they're labelled logically and work as you think they should. You may not need to test every link on a page, but a few is a good idea.
3. do we really care about the structure of the headings?
Yes, we do. Having a proper heading hierarchy is ideal. I believe (but may be wrong) that this relates to WCAG 2.4.6. a blog on the subject is below:
http://webaim.org/techniques/semanticstructure/
4. if the edit field doesn't have any appropriate label, and which is inside the heading level one, will we reported?
I believe so. Form fields should be labelled. See this article for help:
https://www.w3.org/TR/WCAG20-TECHS/H44.html
I hope this makes sense.
Sarah
Sarah Jevnikar
Accessibility Consultant
Digital Echidna
t: 877-858-9604
e: = EMAIL ADDRESS REMOVED =
From: Jennifer Sutton
Date: Thu, Jun 29 2017 8:27AM
Subject: Re: which are the things should keep in mind while doing content testing?
← Previous message | Next message →
Here's an extensive list of tools, and I hope folks who are following
this thread will submit for consideration:
List:
http://www.w3.org/WAI/ER/tools/
Submitting:
http://www.w3.org/WAI/ER/tools/submission
Jennifer
From: Trafford, Logan
Date: Thu, Jun 29 2017 9:37AM
Subject: Re: which are the things should keep in mind while doing content testing?
← Previous message | Next message →
As a somewhat related follow up question:
Does an up-to-date, non-proprietary, testing methodology utilizing some of these tools exist anywhere?
Logan
From: Jennifer Sutton
Date: Thu, Jun 29 2017 9:49AM
Subject: Re: which are the things should keep in mind while doing content testing?
← Previous message | Next message →
I'm not sure I understand what you mean by this question, but here are a
few more things from WAI that may help. And perhaps others will chime in.
Best,
Jennifer
Easy Checks:
http://www.w3.org/WAI/eval/preliminary
WCAG Report Tool:
http://w3c.github.io/wcag-em-report-tool/dist/#/
Template:
http://www.w3.org/WAI/eval/template.html
On 6/29/2017 8:37 AM, Trafford, Logan wrote:
> As a somewhat related follow up question:
> Does an up-to-date, non-proprietary, testing methodology utilizing some of these tools exist anywhere?
>
> Logan
>
>
From: Trafford, Logan
Date: Thu, Jun 29 2017 10:32AM
Subject: Re: which are the things should keep in mind while doing content testing?
← Previous message | Next message →
Thanks Jennifer.
In essence I am looking for the "Easy Checks - A First Review of Web Accessibility" (http://www.w3.org/WAI/eval/preliminary) but expanded to cover all Success Criteria (at least to the AA level).
I've seen a couple that private companies who do evaluation work utilize, but of course those are proprietary. Is there anything available to the general public?
I had created one myself a couple of years ago (for our organization) and am simply looking to compare the one I've created to something else, to ensure its accuracy and current relevance.
Hope that helps explain it better.
Logan
From: timy
Date: Thu, Jun 29 2017 6:01PM
Subject: Re: which are the things should keep in mind while doing content testing?
← Previous message | Next message →
Hi Jennifer,
the below link was really helpful
Thanks for the share.
From: Jonathan Cohn
Date: Fri, Jun 30 2017 7:42AM
Subject: Re: which are the things should keep in mind while doing content testing?
← Previous message | Next message →
I found the FAE at University of Illinois quite useful in highlighting manual checks to do after the automated tests were done. They also have an add-on for Firefox, though I find the add-on a little clunky to use.
Best wishes,
Jonathan Cohn
> On Jun 29, 2017, at 12:32 PM, Trafford, Logan < = EMAIL ADDRESS REMOVED = > wrote:
>
> Thanks Jennifer.
>
> In essence I am looking for the "Easy Checks - A First Review of Web Accessibility" (http://www.w3.org/WAI/eval/preliminary) but expanded to cover all Success Criteria (at least to the AA level).
>
> I've seen a couple that private companies who do evaluation work utilize, but of course those are proprietary. Is there anything available to the general public?
>
> I had created one myself a couple of years ago (for our organization) and am simply looking to compare the one I've created to something else, to ensure its accuracy and current relevance.
>
> Hope that helps explain it better.
>
> Logan
>
>
>
>
>
>
>
>
>
From: Bourne, Sarah (MASSIT)
Date: Fri, Jun 30 2017 12:27PM
Subject: Re: which are the things should keep in mind while doing content testing?
← Previous message | Next message →
> On 6/29/2017 8:37 AM, Trafford, Logan wrote:
>> As a somewhat related follow up question:
>> Does an up-to-date, non-proprietary, testing methodology utilizing some of these tools exist anywhere?
>>
The Department of Homeland Security's Section 508 Compliance Test Processes [1] and the Social Security Administration's Accessibility Best Practices Library [2] are widely used in government.
Many of the newest API-based tools (such as aXe, Tenon, etc.) are designed to be integrated with development tools so you're testing as you work. Having a methodology for them would be a bit like looking for a methodology for spell checking.
[1] https://www.dhs.gov/compliance-test-processes
[2] https://www.ssa.gov/accessibility/bpl/default.htm
Sarah E. Bourne
Director of IT Accessibility, MassIT
Commonwealth of Massachusetts
1 Ashburton Pl. rm 811 Boston MA 02108
617-626-4502
= EMAIL ADDRESS REMOVED =
http://www.mass.gov/MassIT
From: Meacham, Steve - FSA, Kansas City, MO
Date: Fri, Jun 30 2017 1:28PM
Subject: Re: which are the things should keep in mind while doing content testing?
← Previous message | Next message →
This is what I provide to our web developers and testers (hyperlinks are mostly internal, so won't work):
How-to manually inspect HTML pages for Section 508 compliance<https://wiki.tools.fsa.usda.gov/display/508/How-to+manually+inspect+HTML+pages+for+Section+508+compliance>
As a HTML author, developer, or tester, you may feel (mistakenly) that Section 508 compliance testing has to be much more demanding, time consuming, and complicated than it really turns out to be. The testing strategy proposed below is intended to serve as a working approach to evaluate accessibility against Web Content Accessibility Guidelines (WCAG) 2.0<https://wiki.tools.fsa.usda.gov/display/508/Web+Content+Accessibility+Guidelines+%28WCAG%29+2.0> success criteria without requiring a technical background in accessibility or assistive technology.
This procedure is intend to be simple to use and produce results that are consistent with repetitive testing by any tester. In other words, the results are not subjective and the testing and its results may be easily replicated by anyone.
The core procedure does not require special software or specialized skill to perform. HTML inspection requires a knowledge of HTML and some technical acumen. The use of assistive technology is specialized skill and is best performed by an individual who regularly depends on it. When performed fully, this testing procedure can predict, with nearly 100% accuracy, the usability of the software application by persons of all abilities. In addition, the testing results that a tester can document when following this procedure can serve as a comprehensive description of what exact changes must be made to software in order to make it accessible, as well as compliant with Section 508.
Step-by-step Core Procedure (current)
1. Visually inspect each page, and
a. Note any use of color that is the only means of conveying information, (Success Criteria 1.4.1: Use of Color<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.4.1%3A+Use+of+Color>)
b. Note any instructional text that relies solely on sensory characteristics to direct the user; (Success Criteria 1.3.3: Sensory Characteristics<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.3.3%3A+Sensory+Characteristics>)
c. Note any logical divisions or sectioning of the page that lack descriptive headings; (Success Criteria 2.4.1: Bypass Blocks<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.4.1%3A+Bypass+Blocks>)
d. Note any non-English language on the page that are not proper names spelled with initial capital letters; (Success Criteria 3.1.2: Language of Parts<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+3.1.2%3A+Language+of+Parts>)
e. Note any moving, blinking, scrolling, or auto-updating information that cannot be paused, stopped, or hidden; (Success Criteria 2.2.2: Pause, Stop, Hide<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.2.2%3A+Pause%2C+Stop%2C+Hide>)
f. Note any flashing text or images; (Success Criteria 2.3.1: Three Flashes or Below Threshold<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.3.1%3A+Three+Flashes+or+Below+Threshold> or Success Criteria 2.3.2: Three Flashes<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.3.2%3A+Three+Flashes>)
g. Note any hyperlinks that would be insufficiently descriptive if viewed in isolation; (Success Criteria 2.4.4: Link Purpose (In Context)<https://wiki.tools.fsa.usda.gov/pages/viewpage.action?pageIde311581> or Success Criteria 2.4.9: Link Purpose (Link Only)<https://wiki.tools.fsa.usda.gov/pages/viewpage.action?pageIde311591>)
h. Note any headings or labels that are insufficiently descriptive given the context of the current page's title and any enclosing section's heading; (Success Criteria 2.4.6: Headings and Labels<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.4.6%3A+Headings+and+Labels>)
i. Note any navigation or UI elements that appear on other pages that is not identical in its arrangement (Success Criteria 3.2.3: Consistent Navigation<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+3.2.3%3A+Consistent+Navigation>) and identification; (Success Criteria 3.2.4: Consistent Identification<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+3.2.4%3A+Consistent+Identification>)
j. Note any scenarios where a user would be unable to determine what they could or should do, or where they are, in the application or any active workflow. (Success Criteria 2.4.5: Multiple Ways<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.4.5%3A+Multiple+Ways>)
2. Operate each page, and
a. Use the browser to resize the text on the page, and only the text. Enlarge it up to 200% and note any instances where this makes the content illegible; (Success Criteria 1.4.4: Resize text<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.4.4%3A+Resize+text>)
b. If some of the text didn't resize, right click on it to determine if it is actually image, and note if it is; (Success Criteria 1.4.5: Images of Text<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.4.5%3A+Images+of+Text>)
c. Traverse the page using the keyboard's TAB button and verify that all active user interface elements are usable using the keyboard alone; (Success Criteria 2.1.1: Keyboard<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.1.1%3A+Keyboard>)
d. Note any keyboard traps where the focus gets stuck or goes into a loop that prevents the keyboard from navigating away from the trap; (Success Criteria 2.1.2: No Keyboard Trap<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.1.2%3A+No+Keyboard+Trap>)
e. Note whenever the visual focus indicator does not flow in a natural and logical order; (Success Criteria 2.4.3: Focus Order<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.4.3%3A+Focus+Order>)
f. Note whenever the focus indicator is missing or appears in multiple places at the same time; (Success Criteria 2.4.7: Focus Visible<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.4.7%3A+Focus+Visible>)
g. Note whenever the act of shifting focus initiates a change of context or side effect; (Success Criteria 3.2.1: On Focus<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+3.2.1%3A+On+Focus>)
h. Note the absence of skip navigation (visible or invisible) or the ability to bypass any repetitive blocks of content; and (Success Criteria 2.4.1: Bypass Blocks<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+2.4.1%3A+Bypass+Blocks>)
i. Note any elements that, when changed, cause a change of context or side effect, but lack any notification to the user of this effect before they took the action (Success Criteria 3.2.2: On Input<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+3.2.2%3A+On+Input>)
3. Enter erroneous information into any data entry fields and controls, inspect the error messages, and
a. Note any error messages that fail to identify the item that is in error in text; (Success Criteria 3.3.1: Error Identification<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+3.3.1%3A+Error+Identification>)
b. Note any errors where the system should be able to suggest a correction, but doesn't; and (Success Criteria 3.3.3: Error Suggestion<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+3.3.3%3A+Error+Suggestion>)
c. On pages that allow the updating or removal of legal or financial data, ensure that the change is either reversible, checked, or confirmed. (Success Criteria 3.3.4: Error Prevention (Legal, Financial, Data)<https://wiki.tools.fsa.usda.gov/pages/viewpage.action?pageIde311624>)
Extended Procedure to Inspect the HTML to verify semantic markup
HTML inspection requires a knowledge of HTML and some technical acumen, but no special tools.
1. Using the Developer Tools in Internet Explorer, Developer Firefox, or Google Chrome,
a. Note any tables that aren't tables; (Success Criteria 1.3.1: Info and Relationships<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.3.1%3A+Info+and+Relationships>)
b. Any headings that aren't headings; (Success Criteria 1.3.1: Info and Relationships<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.3.1%3A+Info+and+Relationships>)
c. Any labels that aren't labels; (Success Criteria 1.3.1: Info and Relationships<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.3.1%3A+Info+and+Relationships>)
d. Captions that aren't captions; and (Success Criteria 1.3.1: Info and Relationships<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.3.1%3A+Info+and+Relationships>)
e. Any content that originates from CSS ":before" or ":after" specifiers. (Success Criteria 1.3.1: Info and Relationships<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.3.1%3A+Info+and+Relationships>)
Extended Procedure to test operability with Assistive Technologies and alternate browsers
The use of assistive technology is specialized skill and is best performed by an individual with a disability who regularly depends on it.
1. Operate the page with a Screen Reader, FireEyes II's SimuAT, and alternate browsers, and
a. Note any unnatural reading sequences; and (Success Criteria 1.3.2: Meaningful Sequence<https://wiki.tools.fsa.usda.gov/display/508/Success+Criteria+1.3.2%3A+Meaningful+Sequence>)
b. Note any corruption or illegible presentation details. (Guideline 4.1: Compatible<https://wiki.tools.fsa.usda.gov/display/508/Guideline+4.1%3A+Compatible>).
I hope this helps...
Steve Meacham
From: timy
Date: Sun, Jul 02 2017 10:45AM
Subject: Re: which are the things should keep in mind while doing content testing?
← Previous message | No next message
Hi sara and all,
Thanks those who are responded to my questions, and sorry for the
delayed response.
yes, truely said, I am a screen reader user.
some more questions I would like to ask,
kindly answer those.
1. How can I check html code of any of the element in internet
explorer 11?
I tried with control u, but, I couldn't find any of the html tag
unfortunatly while using jaws.
I know focusing any of the element and pressing insert shift f1 will
provide some of the element information (jaws key stroke), but, that
will not be helpful to the developer, right?
Why I am asking because in a webpage, some of the content, the screen
reader is reading as simple text, but, visually it appearing as
heading, told my coleek.
Example of that text:,
sign in with skype
download skype.
if the heading tag is provided like <h1 or whatever, the screen reader
user can easly find it out, right?
2. While checking some of the punctuations like, :, fullstop and comma,
which are the things we should keep in mind?
For example:,
One of the webpage I observe that, they have mentioned like, For
download the skype do the following, then : and, coma, is the right
practice?
or, :, and coma are not necessary there?
3. while providing some of the features of the product, I observe that,
they haven't mentioned the features or, new improvements below the newly
released product name, is it a good practice?
For example:,
Skype version 6.0.
list of three items,
Bullet Screen reader support added.
Bullet now screen reader announce, online and offline status of the user.
Bullet Now you can turn it off time announcement, once the screen reader
user is sending a message pressing f2.
list end.
For better understanding of the screen reader user, can I suggest to
the developer to add reasont improvements are:, or features are: below
the product version?
4. one of the webpage, I observe that, fullstop is provided below the
alternative text for an image, and the spelling also wrong.
So, read the below example and, tell me any reccomentation.
grafic screen soit of first page
.
bit urjent, so, please,
help me out.
With regards,
Timy Sebastian.