New Page

Text alternatives [Recommended]

Text alternatives should describe non-text content such as labels and icons. Similarly, an application should provide captions and where possible audio to accommodate users with hearing and vision disabilities.

Captions for media content [Recommended]

Include captions for pre-recorded audio content. Offer alternative formats and transcripts for videos without subtitles. Add audio descriptions for videos with important visual information.

Color contrast [Recommended]

Ensure sufficient contrast between text and background colors, following WCAG guidelines. Avoid relying solely on color to convey information.

Resizable text [Recommended]

 It should be possible to resize text without assistive technology without loss of content or functionality. This helps people with mild visual disabilities by allowing them to scale text and text-based controls on a web page, without requiring the use of assistive technology.

Clear error messages [Mandatory]

Provide clear and concise error messages with suggested solutions. Ensure error messages are programmatically linked to the corresponding form field. Offer tips or guidance for error correction where possible.

Descriptive titles [Mandatory]

Web pages/app screens should have titles that describe topic or purpose.This facilitates an easy and unambiguous identification of the webpage & also helps in a more relevant and visible presence in the search engine results.

Semantic HTML markup [Mandatory]

Use semantic HTML markup to structure content and provide meaningful information to assistive technologies. Proper use of headings, lists, and landmarks helps users navigate and understand the organization of content.