Assessment for JSTOR by Fanshawe - Module 3: Interface Structure

Submitted by a_thom@fanshawec.ca on
Can the purpose of each link be determined from the link text, or from the link text together with its surrounding context?
Answer: Always
Score: 2
Notes:
Can keyboard focus be moved to all page elements?
Answer: Always
Score: 2
Notes:
If moving keyboard focus away from a component requires more than arrow or tab keys, is this clearly indicated on the page?
Answer: Not Applicable
Score: -1
Notes: Navigation does not require complex key combinations beyond standard tab/arrow usage.
Is default keyboard navigation order logical and intuitive, following the visual flow of the page as described above?
Answer: Always
Score: 2
Notes:
When using a keyboard to navigate the interface, is the keyboard focus indicator visible?
Answer: Always
Score: 2
Notes:
Does all interactive functionality work via keyboard, and does it behave consistently and as expected?
Answer: Always
Score: 2
Notes:
Does focus order move sequentially across form fields?
Answer: Always
Score: 2
Notes:
Do skip navigation controls appear in the same place on every page?
Answer: Sometimes
Score: 1
Notes: Skip link behavior may vary slightly across different sections of the platform.
Does the reader capture accurate information as it appears in the table and the columns and rows?
Answer: Sometimes
Score: 1
Notes: Search results and metadata tables are generally structured well, but complex layouts may not always be perfectly linearized for screen readers.
Does the screen reader successfully navigate from one frame to another?
Answer: Not Applicable
Score: -1
Notes: JSTOR does not rely heavily on traditional frames/iframes for layout.
Does each frame have a meaningful title that tells the user the purpose of the frame?
Answer: Not Applicable
Score: -1
Notes: No significant frame usage detected.
When navigating the page using keyboard navigation, is the user able to navigate effectively from one frame to the next?
Answer: Not Applicable
Score: -1
Notes: Frames are not a core structural element of the interface.
eResource: JSTOR
eResource Type: Database
Vendor: Ithaka
Institution: Fanshawe
Score: A

Key Findings

Strengths

  • All interactive functionality works consistently for users who are navigating a site via keyboard

Weaknesses

  • Screen readers somewhat accurately capture information presented in tables

Navigation Links

Question Answer Notes Images
Can the purpose of each link be determined from the link text, or from the link text together with its surrounding context? Always

Keyboard Navigation

Question Answer Notes Images
Can keyboard focus be moved to all page elements? Always
If moving keyboard focus away from a component requires more than arrow or tab keys, is this clearly indicated on the page? Not Applicable Navigation does not require complex key combinations beyond standard tab/arrow usage.
Is default keyboard navigation order logical and intuitive, following the visual flow of the page as described above? Always
When using a keyboard to navigate the interface, is the keyboard focus indicator visible? Always
Does all interactive functionality work via keyboard, and does it behave consistently and as expected? Always
Does focus order move sequentially across form fields? Always

Skip Links

Question Answer Notes Images
Are there skip links (either visible or invisible)? Sometimes Skip links may be present but are often invisible and only appear on keyboard focus.
Are skip links visible or invisible? Always
Are skip links (visible or invisible) positioned prominently near the beginning of the page? Always
Are skip links labelled properly? Always
Are skip links accessible via keyboard? Always
Do anchors (link destinations) appear at the beginning of the relevant content? Always
Do skip navigation controls appear in the same place on every page? Sometimes Skip link behavior may vary slightly across different sections of the platform.

Tables

Question Answer Notes Images
Does the reader capture accurate information as it appears in the table and the columns and rows? Sometimes Search results and metadata tables are generally structured well, but complex layouts may not always be perfectly linearized for screen readers.

Frames

Question Answer Notes Images
Does the screen reader successfully navigate from one frame to another? Not Applicable JSTOR does not rely heavily on traditional frames/iframes for layout.
Does each frame have a meaningful title that tells the user the purpose of the frame? Not Applicable No significant frame usage detected.
When navigating the page using keyboard navigation, is the user able to navigate effectively from one frame to the next? Not Applicable Frames are not a core structural element of the interface.
Previous1234Next