Accessibility statement

Gorland aims to make its English-language editorial content usable for readers with different abilities, devices, and connection conditions. This statement was reviewed on 5 October 2026. It is written as a standing commitment rather than a one-time technical checklist, since accessibility is treated as part of ordinary editorial quality rather than a separate add-on feature. The statement covers the public pages of the site, including articles, the journal, the resource list, and the contact form, and it is reviewed on the same general schedule as the site's other policies. Gorland does not claim perfect conformance with every accessibility guideline on every page, but it aims to follow recognised practice closely enough that a barrier, when found, is the exception rather than the norm. Readers using a screen reader, a switch device, a low-bandwidth connection, or simple magnification should all be able to reach the core content of an article without needing a specialised workaround. This statement is informed by the general approach of the Web Content Accessibility Guidelines at a conformance level Gorland treats as a practical working target rather than a legal certification, since the site has not undergone a formal third-party audit against that standard. The commitment also extends to readers on a slower mobile data connection common in parts of Indonesia, where a page that depends heavily on large uncompressed images or unnecessary scripts can become a practical barrier even for a reader without any disability. Gorland's editorial and technical processes are not fully separate on this point, since a contributor drafting a new article is expected to apply the same heading and image-description practices described below rather than leaving them to be fixed later. Where a conflict arises between a visual design preference and an accessibility practice described in this statement, the accessibility practice takes priority.

1. Structure

Pages use headings, landmarks, labels, readable contrast, and keyboard-accessible links wherever the platform permits. Headings follow a logical order within each article so that a reader using a screen reader can navigate by heading level rather than having to listen to the entire page from the top. Landmarks such as the main content area, the navigation menu, and the footer are marked in a way that lets assistive technology jump directly to the relevant section. Colour contrast between body text and its background follows the deep charcoal and off-white palette used throughout the site, which was chosen in part because it maintains a comfortable reading contrast rather than relying on a low-contrast decorative tone. Every link and button on the site is reachable using the keyboard's tab key alone, without requiring a mouse, trackpad, or touch gesture to activate it. Form fields on the contact page carry a visible, programmatically associated label rather than relying on placeholder text alone, since placeholder text disappears once a reader begins typing and is not consistently announced by every screen reader. The order in which a keyboard-only reader tabs through a page follows the same logical order as the visual layout, so that tabbing does not jump unexpectedly from the top of the page to the footer and back. Where a page includes a skip-to-content style link for keyboard users, it is one of the first elements a screen reader or keyboard-only reader encounters, allowing the main navigation menu to be bypassed on repeat visits.

(a) Headings: logical order within each page, supporting screen-reader navigation.
(b) Landmarks: main content, navigation, and footer regions are distinguished.
(c) Interaction: every link and control is operable by keyboard alone.
(d) Form labels: visible and programmatically associated, not placeholder text alone.
(e) Tab order: follows the visual layout logically, without unexpected jumps.

2. Images

Editorial images include descriptive alternative text so the visual subject is available in words. Decorative styling is kept separate from meaning. A descriptive alternative text aims to convey the same practical information a sighted reader would take from the image, such as describing a specific exercise posture or a setting relevant to the article, rather than a generic label like "photo" or "image". Where an image is purely decorative and adds no information beyond what the surrounding text already states, it is marked so that assistive technology can skip past it rather than reading an unhelpful description aloud. Gorland avoids embedding meaningful text inside an image file, such as a statistic shown only as a graphic, so that the information remains available to a reader who cannot see the image at all. This approach is reviewed each time a new article is published rather than being applied only retroactively. Writing a useful description is treated as part of drafting the article itself rather than an afterthought added just before publishing, which helps keep the description specific to what the image actually shows rather than a generic restatement of the article's headline. Where an image shows a person performing a movement or exercise, the description typically names the movement and the relevant posture detail, such as stance or arm position, so a reader relying on the description gets comparable practical information to a reader who can see the image directly. Gorland periodically spot-checks a sample of published images against their alternative text as part of the review described in Section 6, to catch a description that may have been copied from a similar image without being adjusted for the specific photo used.

(a) Informative images: descriptive alternative text matching the practical content shown.
(b) Decorative images: marked so assistive technology can skip them.
(c) Text-in-image avoidance: meaningful information is kept in readable text, not embedded graphics.
(d) Description detail: movement and posture named specifically, not a generic restatement of the headline.
(e) Quality check: periodic spot-checks of published images against their alternative text.

3. Motion and interaction

The site avoids unnecessary animation. Navigation can be opened with a keyboard-capable button, and the cookie choice can be selected without pointer-only interaction. Where a small transition is used, such as a menu sliding into view, it is brief and does not rely on rapid flashing or motion that could be uncomfortable for a reader sensitive to such effects. The mobile navigation menu is implemented as a standard button that responds to both a click and a keyboard activation such as the Enter key, rather than requiring a swipe gesture that some input devices cannot perform. Similarly, the cookie banner's Accept and Reject controls are ordinary buttons that can be reached and activated by keyboard, so a reader is not forced to use a mouse simply to dismiss the banner. Gorland does not use auto-playing audio or video with sound, which avoids a common source of disruption for readers using assistive technology that relies on audio output. Interactive elements such as buttons and links are sized with enough surrounding space that a reader with limited fine motor control, using either a touchscreen or a pointing device, has a reasonable target area to activate rather than needing to tap or click with high precision. Focus state, meaning the visible indicator showing which element is currently selected via keyboard, is kept visible rather than removed for visual tidiness, since a hidden focus indicator is a common barrier for a keyboard-only reader trying to track their position on the page. Where a reader's operating system is set to reduce motion, the site's own limited transitions are designed to be unobtrusive enough that they do not meaningfully conflict with that system-level preference.

(a) Animation: brief and limited, avoiding rapid flashing or disorienting motion.
(b) Menu interaction: operable by click or keyboard activation.
(c) Audio: no auto-playing sound that could conflict with assistive technology.
(d) Target size: buttons and links sized with reasonable surrounding space for limited precision input.
(e) Focus visibility: the keyboard focus indicator is kept visible rather than hidden for visual tidiness.

4. Content alternatives

Readers who cannot access a particular presentation may contact the editorial desk for clarification about the published information. If a table, chart, or other visual format on a page is difficult for a reader to interpret with their particular assistive technology, the desk can provide a plain-text description of the same information by email on request. This is intended as a practical bridge for an occasional edge case rather than a sign that the underlying page is being left permanently inaccessible once a gap is identified; where the same kind of request recurs, Gorland treats that as a signal to improve the page format itself. A request of this kind is handled with the same response expectations described in Section 5 below, so a reader is not left waiting indefinitely for a plain-text alternative. This section exists because no single format can anticipate every assistive technology in use, and a direct request is often the fastest way to resolve a specific barrier. A comparison table, such as the one found on terms-related or training-overview pages, is a typical example of a format that benefits from a plain-text alternative for a reader using an older screen reader that does not announce table structure clearly. Where a downloadable resource listed on resources.php is provided only in a fixed visual layout, the desk can describe its contents in the body of an email rather than requiring the reader to open the file itself. Gorland keeps a short internal note of each content-alternative request so that a format causing repeated difficulty can be identified and prioritised for a more lasting fix, consistent with the review process in Section 6.

(a) Example request: a plain-text description of a table or chart.
(b) Response path: the editorial desk, by email, on a case-by-case basis.
(c) Recurring requests: treated as a signal to revise the page format itself.
(d) Typical example: a comparison table described in plain text for an older screen reader.
(e) Internal tracking: each request noted so a repeatedly difficult format can be prioritised for a fix.

5. Feedback

Send an accessibility concern to [email protected] or +62 857 2309 4185. Please identify the page, device or assistive technology, and the barrier observed. Gorland aims to acknowledge an accessibility report within 5 business days, which is faster than the general response target used for some other inquiries, because an accessibility barrier can prevent a reader from accessing the site at all. Where possible, the desk will provide a temporary workaround, such as a direct plain-text answer to the underlying question, while a more permanent fix to the page is scheduled. Including the specific device, browser, and assistive technology in use, such as a particular screen reader and browser combination, makes it significantly easier for the team to reproduce and resolve the barrier. Reports that cannot be reproduced with the information provided will prompt a follow-up question rather than being closed without a response. A report describing a specific barrier, such as a heading that is skipped when navigating by heading level, is generally resolved faster than a more general comment about the site's overall usability, simply because a specific report is easier to reproduce and verify as fixed. Gorland treats an accessibility report as distinct from a general feedback message and routes it to whoever on the team is responsible for the technical implementation of the affected page, rather than only to the editorial desk. A reader who does not receive an acknowledgement within the 5-business-day target is encouraged to follow up by phone using the number above, in case the original message was affected by a delivery issue on either side.

(a) Acknowledgement target: within 5 business days.
(b) Helpful detail: page, device, browser, and assistive technology used.
(c) Interim support: a direct plain-text answer while a permanent fix is scheduled.
(d) Routing: a specific, reproducible barrier is routed to the person responsible for that page's implementation.
(e) No acknowledgement received: follow up by phone in case of a delivery issue.

6. Review

Reported barriers are assessed in the ordinary editorial workflow. A future revision will carry its own dated note. An assessed barrier is prioritised according to how many readers it is likely to affect and how severely it blocks access to the underlying content, rather than being addressed strictly in the order reports are received. Where a reported barrier leads to a structural change, such as revising how a table is marked up across multiple articles, the change is applied consistently rather than only to the single page that prompted the report. This statement's own review date will be updated whenever a material change is made to the accessibility practices described above, separately from routine article publishing. A reader who reported a barrier in the past is welcome to check back on this page or ask directly whether a specific issue has since been resolved. A barrier that affects a widely read page, such as one linked from the homepage, is generally prioritised ahead of a similar barrier on a less-visited page, simply because the practical impact on readers is larger, though a severe barrier on any page, such as one that prevents a reader from submitting the contact form at all, is treated as high priority regardless of how often that particular page is visited. Gorland does not currently publish a separate changelog specific to accessibility fixes, but a reader who wants confirmation that a particular reported issue has been addressed may ask the editorial desk directly rather than needing to infer it from the review date alone. This review process applies to the site's existing pages as well as to any new page added in the future, so a newly published article is expected to meet the same standard described in Sections 1 through 4 before publication, not only after a reader reports a gap.

(a) Prioritisation: based on likely reach and severity of the barrier.
(b) Structural fixes: applied consistently across affected pages, not only the one reported.
(c) Status check: readers may ask directly whether a previously reported barrier has been resolved.
(d) High-priority example: a barrier preventing use of the contact form, regardless of page traffic.
(e) New content standard: a newly published page is expected to meet this statement before publication.