Various rendering modalities

Open
#32 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
30/100
Issue type
Feature
Clarity
Mostly clear
Activity status
Stale
Tech stack
html
Domain
accessibility, documentation

Research direction

Compare the abstract and introduction with the normative sections that currently discuss SVG and PDF. Decide whether HTML, screen-reader, braille, and radio-frequency rendering are in scope or whether the introduction should describe an extensible framework. Done means the introductory claims and normative content agree.

Written by the indexing model from the issue text.

Description

The abstract (and the introduction) of the specification says:

This specification describes mechanisms that can be used to represent a Verifiable Credential through a visual, auditory, or haptic medium. It covers rendering a Verifiable Credential to a physical document, digital image, radio frequency, screen reader, or braille output.

My question is whether the spec will indeed include types for, e.g., screen readers and braille output. At this moment, it talks about SVG and PDF, it does not even include anything with pure HTML (that could be used with screen readers) let alone braille or radio frequency. (One could say that Digital Image is covered by SVG, although this may not be what is expected either.)

There should be no discrepancy between the introductory parts and the normative content. Either we should signal the fact that we work on these, or change the intro part making it clear that for some of these modalities we just offer a framework where other communities may plug their rendering methods.

(I realize it is more work, but I would actually find it great if braille and HTML rendering was also included...)

Dominant language
HTML
Stars
9
Forks
8
Avg merge
14d 42m
Merged PRs (30d)
2

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from w3c/vc-render-method

All issues in w3c/vc-render-method

Similar issues

More Accessibility issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.