Day 6 - Accessibility Testing - WCAG Success Criteria - Text Zoom

By -

What I Accomplished Today...
Today, I wanted to understand WCAG Success Criteria – Resize Text

  
What I Learned Today...
Not everyone uses your site at the default size as it was designed. 

Many people with visual impairments use zoom in order to see the content. It is important to check that website still works even when it's zoomed in.

This is part of the WCAG success criterion: 1.4.4 Resize Text.

Technical Skills Required: Zero

Testing Steps:
  • Open a website on your desktop browser. (Ex: Chrome) 
  • Zoom your browser website page to 200% (or) In browser's settings - Appearance - Page Zoom: 200%
  • See what happens to the content and layout of the webpage.

Observe & Take notes:
  • Is all the content still present on the page and is it still in an order that makes sense?
  • Does any of the content overlap or appears far apart?
  • Do navigation bars or menus get replaced with mobile-style Hamburger menus?
  • Does the page adapt to the new viewing dimensions? Does the content start to stack vertically instead of using a lot of space horizontally?
  • Do you have to scroll horizontally to read everything? Is it impacting your browser experience?
  • This is an important one: Is everything still working? Links, buttons, forms, and menus still function with the content zoomed?
  • Test with Screen Reader, as people with low vision, will combine with assistive technologies to read the content after zoom in.
  • Can able to access the website with Key-board only?

Common Errors:
  1. The website Layout does not look properly
  2. Website Content is lost/does not display properly
  3. Images and content overlap.
  4. Text in form controls does not zoom in to 200%.

Rules:
This rule checks that the meta element retains the user agent's ability to zoom.

Check Developer Tools - Elements Tab:
<meta name="viewport" content="width=device-width, initial-scale=1,
maximum-scale=2.0, user-scalable=yes">

This viewport meta element allows users to scale content up to 200%
because it has a maximum-scale set to 2.0 and does not prevent user scaling because it has a user-scalable set to yes.

Location: Bengaluru, Karnataka, India

Popular Posts

JMeter Producing Error: Windows RegCreateKeyEx(...) returned error code 5

By -
After running JMeter.bat on Command Line, Problem java.util.prefs.WindowsPreferences <init> WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0x80000002. Windows RegCreateKeyEx(...) returned error code 5. Cause Environment Resolving the problem The error occurs because java.util.prefs.WindowsPreferences is trying to save information in HKEY_LOCAL_MACHINE\Software\JavaSoft\Prefs instead of under HKEY_CURRENT_USER\Software\JavaSoft\Prefs. Windows 7 64-bit The work around is to Open JMeter.bat file as the administrator and so it creates the key HKEY_LOCAL_MACHINE\Software\JavaSoft\Prefs.
Read more

Understanding about Contract Testing

By -
Image
Yesterday Morning (9th May 2020), I had good discussion with  Sundaresan  Krishnaswami on " Contract Testing ". I thank  Sundaresan   for his time and sharing his knowledge. It started with an example: The Owner provides the house or Place of Residence to the Tenants. "Rent Agreement" is provided for the house and It contains agreement to use the house. The house comes with like kitchen, living room, bed room, fans, geysers etc.. It also contains who resides and what is the contractual period, obligation (money) etc.. Here, Owner is the Server and Tenant is Client.                                         Client-Server Architecture. Illustrating the same in the E-Commerce Context: In Some Development Companies, There can be two teams developing the Payments and Orders APIs. In B2B or B2C Ecommerce applications, we place an order using web browser through payment methods and Order is created. Order is successful only when Payment is successful. In general, Payments te
Read more