Closed Bug 369082 Opened 14 years ago Closed 4 years ago

expose IA2 localizeXXX methods

Categories

(Core :: Disability Access APIs, defect)

defect
Not set
normal

Tracking

()

RESOLVED INCOMPLETE

People

(Reporter: surkov, Unassigned)

Details

(Whiteboard: [auto-closed:inactivity])

Does accessible module has a place where .properties files should be places? If it hasn't then should accessible have own package?
Blocks: 347791
Blocks: ia2
We have these:
http://lxr.mozilla.org/seamonkey/find?string=accessible.properties

But the truth is that most things should not be localized -- even our actions. Otherwise when AT goes to look for a specific action, such as "toggle" to find out  a tree cell checkable, then it can't find it.

Most of the localization stuff is in there for the future, when web authors will be able to define their own roles.
So, should be localized values of methods localizedRoleName, localizedStateNames, localizedExtendedRole, localizedExtendedStates?
I don't think we'll need those for now.

In the future web authors may want to create new kinds of accessibility roles, which are basically classes. The roles will need to be able to support various properties, relations, actions, etc. All of those things will have to have author-supplied localized names.

For the built-in semantics the AT is responsible for the localization. If the API makes it look different it's a problem with the API, and we should report it.
I just like to have bug 347791 fixed. For this I need to get string representation  of role, states.
That's different. See my last comment in that bug. We should be exposing the programmatic constant, since the information is consumed by other programmers.
Blocks: 371591
No longer blocks: ia2
I thought that AT use rather constants than their localized names, for example, they would use nsIAccessible::role than localizedRoleName. Wouldn't it?

What should localizedRoleName return?
Assignee: aaronleventhal → surkov.alexander
We won't need localizedRoleName for Firefox 3. I think returning E_NOIMPL would be correct for now.

In the future this will allow web authors to define new widgets. We'll also need to find a way to expose the inheritance hierarchy for the widget they define, as well as whatever custom properties/interfaces etc. it has.
> In the future this will allow web authors to define new widgets.

Let me clarify. In the future an author could perhaps define a new role somewhere, call it "myroles:calendar". It might inherit from "grid". They'll need to expose the localized version of "calendar" somewhere, so that the screen reader knows how to tell the user what it is, even if it hasn't ever seen one before.
Same thing with states/relations. That's for authors defining new properties, which isn't possible with ARIA yet.
No longer blocks: 347791
(In reply to comment #10)
> Same thing with states/relations. That's for authors defining new properties,
> which isn't possible with ARIA yet.
> 

Does it mean we won't provide localized versions of reserved relations/actions? And all this methods are going to be used only when ARIA gets an ability to specify this?
No longer blocks: 371591
Yes. At least for now we don't need this.
This sounds like accessible.properties should not be looked into and just be cvs rm'ed? Which would make bug 374605 WORKSFORME or something.
Assignee: surkov.alexander → nobody
AUTO-CLOSED. This bug untouched for over 2000 days. Please reopen if you can confirm the bug and help it progress.
Status: NEW → RESOLVED
Closed: 4 years ago
Resolution: --- → INCOMPLETE
Whiteboard: [auto-closed:inactivity]
You need to log in before you can comment on or make changes to this bug.