You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Visually impaired people who rely on screen readers will be impacted while navigating the page in heading mode if the heading structure of the page is not defined in a logical sequence i.e., h1>h2>h3>h4>h5>h6.
Note: User credentials should Not be included in the bug.
Accessibility Insights! - Identify accessibility bugs before check-in and make bug fixing faster and easier.
External Bug Process: If this bug belongs to external team, mark it as resolved/done and assign it back to the tester with notes on where to file/route the bug. For more information, please use this Link. “HCL Staff should not log any third-party external bugs. Should be routed to EDAD team”.
User Impact:
Visually impaired people who rely on screen readers will be impacted while navigating the page in heading mode if the heading structure of the page is not defined in a logical sequence i.e., h1>h2>h3>h4>h5>h6.
Note: User credentials should Not be included in the bug.
Repro Steps:
Actual Result:
heading hierarchy is not followed on the page.
Expected Result:
'burrashiva01/ff', 'History' and 'Release zone' text should define in h2 heading level.
MAS Reference:
MAS 1.3.1 – Info and Relationships
Reference Links:
The text was updated successfully, but these errors were encountered: