List view

• Accessibility Review

  Issues related to map accessibility

  No due date

  •0/2 issues closed
  0% complete2 open0 closed

• Autumn 2024

  Bug fixing and important a11y improvements

  Overdue by 6 month(s)

  •

  Due by December 20, 2024

  •14/26 issues closed
  53% complete12 open14 closed

• Implement MapML vocabulary as custom elements

  For those that make sense, now that we've refactored the vocabulary entirely to the custom elements' `map-` 'namespace', we should define the behaviour and implement the elements of the MapML vocabulary as actual custom elements modules. This milestone will contain issues for individual elements as they arise.

  No due date

  •2/3 issues closed
  66% complete1 open2 closed

• v1.0.0

  This milestone intends to capture a project state in which - all [capabilities that have been deemed requirements](https://maps4html.org/HTML-Map-Element-UseCases-Requirements/#requirements) and that can be polyfilled are implemented - [Web Platform Tests](https://github.com/Maps4HTML/Web-Map-Custom-Element/projects/2#card-43799737) have been designed to validate browser interop for the proposal have been implemented against the polyfill, ready for porting to implementation-ready versions of the WPT suite - implement full vocabulary as Custom Elements - other tbd pls discuss

  No due date

  •1/3 issues closed
  33% complete2 open1 closed

• Make use of MapML self-perpetuating

  The idea is that like the old "View Source" notion, users of a Web map built with MapML should be able to copy-and-paste idiomatic structures so they can be re-used and re-purposed by users, in a user-becomes-developer scenario. We can facilitate this to some extent, by providing affordances to achieve narrower tasks. Examples might include copying the current extent via a menu option, as a MapML `<meta name="extent" content="...">`, or copying a `<feature >` element.

  No due date

  •1/2 issues closed
  50% complete1 open1 closed