Skip to content

Feature/a11y terms #529

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 7 commits into from
May 21, 2025
Merged

Feature/a11y terms #529

merged 7 commits into from
May 21, 2025

Conversation

klngwll
Copy link
Contributor

@klngwll klngwll commented May 16, 2025

Follow up on #526

  • Dust off subcClasses for ContentAccessibility based on schema terms. Keep properties out off KBV for now only using contentAccessibility as "container" within the Bib-frame. Easier to add more properties than remove if needed later. For now we use blank nodes.

In this PR also draft for linked terms. (Need more work)

  • Add a11y-terms.ttl with terms for features, hazards, mode and mode sufficient. Not in this PR: publishing on id.kb.se
  • Suggestion on form combining accessModeSufficient terms
  • Links to documents forming the basis included for traceability. Definitions and labels in english have been added from these where most suitable atm.
  • Add unstable status to terms indicating all things are moving, also in international groups regarding presentation and combinations of terms. This is the first step to comply with EAA. We might need to revise and improve later, and find suitable ambition for overlaps with normalization issues etc.

See FMT-26 for details.

Copy link
Member

@niklasl niklasl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM! Let's start with this and work on finalizing the terms (tacking standard alignments/cross-walks) for subsequent publication.

@klngwll klngwll merged commit 3d9071b into develop May 21, 2025
@klngwll klngwll deleted the feature/a11y-terms branch May 21, 2025 15:07
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants