@hellstromgu wrote:...
FYI @gregg I've proposed what I think is a simple solution in #445 (closed). Since this issue (#92 (closed)) is closed, I'd prefer to continue the ...
A colleague pointed out that 3GPP may have a separate requirement for 800 characters, but I don't have the reference handy. That may be another con...
Resolution Proposal:...
FYI I filed the above comments as #445 (closed).
In addition to being arbitrarily prescriptive, these new limit proposals conflict with other EN and WCAG recommendations to allow enough time in EN...
I don't see these limit expectations as either necessary or desirable. Among other negative side effects, these new expectations would arbitrarily ...
Editorial suggestion to reduce redundancy:...
I think it will be challenging to modify SC 3.2.6 or write a new requirement that will rule out "bad" design, allow purposeful navigation changes, ...
There should be an app exception in the scenario where the platform accessibility API does not support this requirement. For example, most "Smart T...
The final report and recommendations of the US Hearing Aid Compatibility Task Force (HAC TF) [site:fcc.gov] is relevant here. In addition to the ex...
One point raised in the STF call today was that including network "supplementary services" may include some ambiguities such as, ~"network voicema...
Note that the above clarification about using ~"minimum number of characters" instead of ~"minimum file size" was to be inclusive of double-byte ch...
See related #242 "Add definition: continuous real-time conversation (from TR 103 708)"
About
Pronouns: he/him