- From: ABHIRUP SINHA <sinha.abhirup@gmail.com>
- Date: Mon, 12 Feb 2018 12:25:37 -0500
- To: public-agwg-comments@w3.org
- Message-ID: <CABX8TnzD5DeTteXDtx0ncnaNTn0xPnvo7EKiehy1e8avdfeArA@mail.gmail.com>
Hello, This is Abhirup Sinha employee of Tata Consultancy Services, currently working on Delta Airlines Inc. and Virgin Atlantic as Accessibility QA Lead. I was going through the all new recommendation of WCAG2.1 and one point came in to my mind that time. Here this is: I want to put one point on one of the recommended WCAG2.1 guideline. I am describing my point and suggestion below. Please feel free to contact me if you need any other info on these. *Guideline:* 3.2.6 Status Changes <https://www.w3.org/TR/WCAG21/#status-changes> *Scenario:* In current world it’s all about web. Sometime we get status changes of any particular application or Order. This specific ‘status change’ came to my mind when I ordered pizza from one of the service provider. After ordering pizza you could able to track or check the status of your order online. And if you stay on that page you could see the ‘change of status’ starting from “ORDER RECEIVE” to “OUT FOR DELIVERY” without any refresh of that page. Here I am posting some images from web (Sorry I am not ordering now! Its office time J ) [image: Inline image 1] [image: Inline image 2] So *Success criterion* will be for this: If in any web page Dynamic Status Bar/Status Message is there which changes with time without refreshing the page, then SR should focus and read the ‘change of the status’ once it got change to new status. Have a nice day! -- Thanks & Regards *Abhirup Sinha* *Atlanta, USA* *+1-4043752334*
Attachments
- image/png attachment: image.png
- image/png attachment: 02-image.png
Received on Tuesday, 13 February 2018 08:23:39 UTC