Accessibility
Verse & Variable
A line of verse. A line of inquiry.
لفظ سے لہر تک — Lafz se Lehar tak
1. Our Commitment
Verse & Variable believes that literature, language, knowledge, and intellectual exploration should be accessible to as many people as possible.
A literary archive that brings together different languages, scripts, cultural traditions, and scientific perspectives must consider the diversity of its readers. Accessibility is therefore an editorial and technical responsibility, not merely a visual-design preference.
We aim to make this publication usable by people with different visual, auditory, motor, cognitive, and learning requirements, including people who use assistive technologies.
Accessibility will be considered throughout the development of the website, the presentation of literary works, the selection of typography, and the publication of scientific commentary.
2. Accessibility Standard and Scope
The publication uses the Web Content Accessibility Guidelines (WCAG) 2.2 Level AA as its principal accessibility reference.
The relevant guidelines are available from the World Wide Web Consortium:
Our objective is to work progressively towards WCAG 2.2 Level AA conformance across the complete website, including its pages, interactive components, responsive layouts, and different language presentations.
This statement describes an accessibility objective. It is not an independent accessibility audit, a certification, or a declaration that every published page currently satisfies every WCAG success criterion.
Third-party services, external resources, and content outside the publication’s control may have separate accessibility limitations.
3. Four Accessibility Principles
Our accessibility approach follows four connected principles.
3.1 Perceivable
Information should be available through more than one sensory channel wherever reasonably possible.
We aim to provide:
- Readable text with sufficient contrast.
- Meaningful alternative text for informative images.
- Clear visual distinction between headings, paragraphs, quotations, and metadata.
- Text alternatives for meaningful visual information.
- Captions or transcripts where audio and video content is published.
- Content that remains usable when enlarged or displayed with modified visual settings.
Scientific illustrations and wavefield visualisations should not be the only means of communicating important information.
3.2 Operable
Visitors should be able to navigate and interact with the website through different input methods.
We aim to support:
- Keyboard navigation.
- Visible keyboard focus.
- Logical focus order.
- Clear navigation and interactive controls.
- Sufficiently large and distinguishable interactive targets.
- Functional alternatives to mouse-dependent interactions.
- Reduced-motion preferences wherever animation is used.
No essential article content should depend exclusively on hover effects, animated backgrounds, or pointer interactions.
3.3 Understandable
The organisation and presentation of information should remain predictable and comprehensible.
We aim to provide:
- Descriptive page titles and headings.
- Consistent navigation.
- Clear link names and control labels.
- Proper language identification.
- Distinctions between original literary text, transliteration, translation, commentary, and scientific interpretation.
- Explanations of specialised terminology where appropriate.
Literary interpretation may be nuanced, but the structure of its presentation should remain clear.
3.4 Robust
The website should be structured so that browsers, assistive technologies, and other reading systems can interpret its content reliably.
We aim to use:
- Semantic HTML.
- Correct heading hierarchy.
- Appropriate language and text-direction metadata.
- Accessible names for controls.
- Meaningful document structure.
- Progressive enhancement where practical.
- Standards-based markup and responsive layouts.
4. Multilingual Accessibility
Verse & Variable publishes and discusses literary works in several languages, including Urdu, Hindi, Marathi, Kannada, Tamil, Malayalam, and Telugu.
Accessibility across languages requires attention to the writing system, language identification, character rendering, reading order, and the linguistic context of each passage.
4.1 Language Identification
The primary language of each page should be identified programmatically.
Where a passage, quotation, title, or translation uses another language, its language should be identified wherever technically and editorially appropriate.
This helps screen readers and other assistive technologies apply suitable pronunciation and language-processing rules.
Original literary language should not be replaced by an English translation merely to simplify presentation.
4.2 Original Scripts and Transliteration
Original scripts are an essential part of literary expression and cultural identity.
Where appropriate, articles may provide:
- Original text in its native script.
- Transliteration into Latin script.
- English translation.
- Explanatory notes and attribution.
Transliteration and translation should supplement the original rather than silently replace it.
Readers should be able to distinguish these layers clearly.
4.3 Script Rendering and Typography
Typography should support the distinctive characteristics of each writing system.
We aim to ensure that:
- Characters and combining marks render correctly.
- Words and glyphs are not unintentionally clipped.
- Line spacing accommodates scripts with complex vertical forms.
- Font fallbacks remain usable when external fonts fail to load.
- Text remains readable at different sizes and screen widths.
- Regional scripts are not treated as decorative visual elements.
Specialised fonts may improve presentation, but the publication should not depend on a single external font for the legibility of its content.
5. Urdu and Right-to-Left Presentation
Urdu requires particular care because its writing direction and typographic conventions differ from those of left-to-right languages.
The publication uses Urdu’s original script and aims to preserve its natural reading direction and literary presentation.
We aim to ensure that:
- Urdu passages use right-to-left text direction.
- The language is correctly identified as Urdu.
- Nastaliq typography is presented with adequate line height and spacing.
- Punctuation, numerals, and mixed-language passages are handled carefully.
- English commentary and Urdu quotations maintain their intended reading order.
- Text alignment and direction do not create confusion for screen-reader users.
- Urdu content remains readable when the preferred font is unavailable.
Mixed-direction passages should be structured so that embedded English words, dates, numbers, and technical expressions do not unexpectedly reorder surrounding Urdu text.
The publication recognises that a right-to-left script is not simply left-to-right text with right alignment. Direction, language metadata, font selection, and bidirectional text handling must work together.
6. Readability, Contrast, and Visual Design
The visual identity of Verse & Variable is intended to support sustained reading rather than compete with literary content.
We aim to maintain:
- Sufficient contrast between text and background.
- Consistent visual hierarchy.
- Comfortable paragraph width.
- Readable font sizes.
- Adequate spacing between paragraphs and sections.
- Clearly distinguishable links and interactive controls.
- Responsive layouts for mobile, tablet, and desktop screens.
As a general WCAG 2.2 Level AA reference, normal text should meet a contrast ratio of at least 4.5:1, while large text should meet at least 3:1, subject to the standard’s stated exceptions.
Colour should not be the sole means of communicating meaning, status, or distinctions.
Readers should be able to enlarge text using browser settings without losing access to essential content or functionality.
7. Keyboard Navigation and Interaction
The website should remain navigable without a mouse.
We aim to support:
- Access to primary navigation through the keyboard.
- A visible focus indicator.
- Logical movement between interactive elements.
- A skip link to bypass repeated navigation.
- Keyboard-accessible theme controls and menus.
- No keyboard traps.
- Clear identification of interactive elements.
Interactive components should use appropriate semantic elements and should not rely on custom pointer-only behaviour.
Where a control cannot be operated through the keyboard, an accessible alternative should be considered.
8. Screen Readers and Assistive Technologies
The publication aims to support visitors who use screen readers, magnification tools, speech recognition, switch devices, and other assistive technologies.
We aim to provide:
- Semantic landmarks for navigation and page content.
- Descriptive headings and hierarchical structure.
- Meaningful link text.
- Appropriate labels for controls.
- Useful alternative text for informative images.
- Empty alternative text for purely decorative images where appropriate.
- Accessible descriptions for complex scientific illustrations.
- Correct language and text-direction information.
Decorative visual elements, including animated backgrounds, should not create unnecessary announcements or interfere with access to the actual article.
Scientific figures should communicate their essential meaning through captions, surrounding explanations, or text alternatives rather than requiring readers to interpret an image alone.
9. Motion, Animation, and Visualisations
The publication may use animated wavefields, visual effects, and scientific illustrations to complement its literary and scientific themes.
These elements are supplementary.
We aim to:
- Respect the user’s reduced-motion preferences.
- Avoid unnecessary motion and flashing effects.
- Ensure that essential content remains available when animation is disabled.
- Avoid using animation as the sole carrier of information.
- Keep decorative motion separate from the main reading experience.
- Provide a textual explanation of meaningful scientific visualisations.
A reader should be able to understand an article without watching an animated background or interacting with a visual simulation.
10. Audio, Video, and Multimedia
Where audio or video material is included, accessibility should be considered before publication.
Depending on the material, this may include:
- Captions for spoken content.
- Transcripts for audio recordings.
- Descriptive text for important visual information.
- Clear identification of speakers and performers.
- Controls that can be operated using a keyboard.
- Avoidance of unexpected or uncontrolled autoplay.
Literary performances, musical recordings, and spoken poetry should retain their artistic context while providing reasonable text-based access to their content.
The publication will also respect the rights of performers, creators, and rights holders when providing supplementary material.
11. Editorial Accessibility
Accessibility also depends on how material is written and organised.
Editorial practice should aim to:
- Use descriptive headings rather than relying only on visual formatting.
- Keep paragraphs and sections logically organised.
- Explain specialised scientific terminology where necessary.
- Distinguish quotation from commentary.
- Identify original language, translation, transliteration, and attribution.
- Avoid unnecessary visual clutter.
- Provide meaningful captions and descriptions for illustrations.
- Maintain clarity without flattening the literary or intellectual complexity of the work.
Scientific explanations should remain accessible without sacrificing technical accuracy.
12. Accessibility Testing and Improvement
Accessibility is an ongoing responsibility.
As the website develops, we aim to assess it through a combination of automated checks and human review.
Where practical, review may include:
- Keyboard-only navigation.
- Screen-reader testing.
- Browser zoom and text enlargement.
- Responsive layout checks.
- Colour contrast evaluation.
- Reduced-motion testing.
- Inspection of language and direction metadata.
- Validation of semantic HTML.
- Review of image alternatives and multimedia transcripts.
Automated testing can identify some technical issues but cannot establish accessibility on its own. Manual review and, where possible, feedback from people who use assistive technologies are also important.
Identified barriers should be prioritised and corrected as development continues.
13. Known Limitations
The publication is a developing project. Some pages, scripts, fonts, animations, external resources, and older content may not yet satisfy every accessibility objective described in this policy.
Third-party platforms and externally hosted resources may introduce limitations beyond the publication’s direct control.
Where a limitation becomes known, the intention is to document and address it rather than imply that accessibility is already complete.
14. Feedback and Accessibility Concerns
Readers are encouraged to report accessibility barriers, including:
- Incorrect reading order.
- Inaccessible navigation or controls.
- Problems with Urdu or other regional scripts.
- Missing or misleading image descriptions.
- Text contrast or readability issues.
- Screen-reader compatibility problems.
- Motion-related difficulties.
- Content that is difficult to understand because of its presentation.
Reports should identify the affected page and, where possible, describe the browser, assistive technology, or interaction that caused the difficulty.
Accessibility feedback can be sent through the editor’s official website:
https://sites.google.com/view/pravinkumarghodake
Feedback will be considered as part of the publication’s ongoing development.
15. Review of This Policy
This policy may be revised as the website, its technical infrastructure, and its editorial practices evolve.
The intention is to make accessibility a continuing part of the publication’s design, maintenance, and growth.
Verse & Variable
A line of verse. A line of inquiry.
لفظ سے لہر تک — Lafz se Lehar tak